Large data management in communication applications through multiple mailboxes

ABSTRACT

Technologies are described to increase a data limit for a user of a communication application by introducing additional archive mailboxes as the original archive fills up or subsequently added archive mailboxes fill up. Thus, a user&#39;s data limit may be effectively removed through the use of N additional archive mailboxes. The additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application or associated service. In other examples, additional mailboxes may be used to add to the capacity of the primary mailbox (cached) as well.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/737,454, filed Jun. 11, 2015, which claims priority to U.S. Provisional Patent Application No. 62/130,475, filed Mar. 9, 2015, the contents of both are incorporated by reference herein.

BACKGROUND

Communication applications enable two or more users to communicate electronically using multiple modes of communication such as email, text messaging, media exchange, audio communication, video communication, desktop sharing, data sharing, application sharing, and similar modes. Some communication applications include additional functionality such as scheduling, contact list management, task management and comparable ones. Items such as emails, exchanged text messages, contacts, calendar items, etc. may be saved in special storage containers called mailboxes. Due to the increase in the used communication modes, shared amounts of data, and expansion of electronic communications, data generated by the communication applications may reach large amounts fairly rapidly. Due to design considerations, memory limitations, and other factors, mailboxes are typically limited to predefined capacities, however.

For example, in some email applications, user mailboxes may be limited to 100 or 200 GB. Some communication applications may provide a primary mailbox and an online archive mailbox, where older items may be moved from the primary mailbox. However, the archive mailboxes typically have similar size limitations as primary mailboxes. Thus, users generating large amounts of communication data may hit the limits fast degrading their user experience. Conventional solutions include manual or automatic export of data from the communication application to other data storages (e.g., regular file folders), but such exported data is usually not readily available to the communication application making this type of remedy not satisfactory for users.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to exclusively identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Embodiments are directed to large data management in a communication application through multiple mailboxes. In some examples, a predefined size threshold of an online archive mailbox of associated with a user being reached may be detected. Upon detection, one or more additional online archive mailboxes may be created for the user. Communication application related data may then be stored in the one or more additional online archive mailboxes, where data in the online archive mailbox and in the one or more additional online archive mailboxes may be available for one or more functionalities of the communication application in a transparent manner to the user.

These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory and do not restrict aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A through 1C illustrate example configurations in implementation of large data management in a communication application through multiple mailboxes;

FIG. 2 illustrates an example user experience for an administrator of a communication service implementing large data management through multiple mailboxes;

FIG. 3 illustrates example operations on a communication system with multiple mailboxes;

FIG. 4 is a simplified networked environment, where a system according to embodiments may be implemented;

FIG. 5 is a block diagram of an example computing device, which may be used to implement large data management in a communication application through multiple mailboxes; and

FIG. 6 illustrates a logic flow diagram of a method to provide large data management in a communication application through multiple mailboxes, according to embodiments.

DETAILED DESCRIPTION

As briefly described above, data limit for a user may be increased by introducing additional archive mailboxes as the original archive fills up or subsequently added archive mailboxes fill up. Thus, a user's data limit may be effectively removed through the use of N additional archive mailboxes. The additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application or associated service. In other examples, additional mailboxes may be used to add to the capacity of the primary mailbox (cached) as well.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations, specific embodiments, or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.

While some embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a personal computer, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Some embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es). The computer-readable storage medium is a computer-readable memory device. The computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, a flash drive, a floppy disk, or a compact disk, and comparable hardware media.

Throughout this specification, the term “platform” may be a combination of software and hardware components to provide a communication application or service with mailboxes to store data. Examples of platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems. The term “server” generally refers to a computing device executing one or more software programs typically in a networked environment. More detail on these technologies and example operations is provided below.

A computing device, as used herein, refers to a device comprising at least a memory and a processor that includes a desktop computer, a laptop computer, a tablet computer, a smart phone, a vehicle mount computer, or a wearable computer. A memory may be a removable or non-removable component of a computing device configured to store one or more instructions to be executed by one or more processors. A processor may be a component of a computing device coupled to a memory and configured to execute programs in conjunction with instructions stored by the memory. A file is any form of structured data that is associated with audio, video, or similar content. An operating system is a system configured to manage hardware and software components of a computing device that provides common services and applications. An integrated module is a component of an application or service that is integrated within the application or service such that the application or service is configured to execute the component. A computer-readable memory device is a physical computer-readable storage medium implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, a flash drive, a floppy disk, or a compact disk, and comparable hardware media that includes instructions thereon to automatically save content to a location. A user experience—a visual display associated with an application or service through which a user interacts with the application or service. A user action refers to an interaction between a user and a user experience of an application or a user experience provided by a service that includes one of touch input, gesture input, voice command, eye tracking, gyroscopic input, pen input, mouse input, and keyboards input. An application programming interface (API) may be a set of routines, protocols, and tools for an application or service that enable the application or service to interact or communicate with one or more other applications and services managed by separate entities.

FIG. 1A through 1C illustrate example configurations in implementation of large data management in a communication application through multiple mailboxes.

Some communication applications/services may have technical hurdles that may prevent increasing the quota of mailbox container per user to large amounts (for example, 2 TB vs. current limits of 200 GB). Maximum mailbox size may be restricted by physical size of disk and total number of items per folder in a mailbox may be restricted due to performance considerations while indexing items and/or creating views. A maximum folder depth per mailbox may be restricted due to performance considerations for mailbox processing. Furthermore, a communication service may not have the ability to have more than two mailboxes per user (one primary and one archive mailbox) in some examples.

A service according to embodiments may be implemented on one or more servers 102 and facilitate communications between users (or subscribers) such as user 108 over one or more networks 106. The communication service may be accessed through thin clients such as web browsers on individual client devices or through thick clients (locally installed applications with more capabilities) such as mail application 110 on computing device 109. Some or all of the data associated with the service may be stored in data stores 104 and/or local data stores on client devices. While mail application 110 is used as an example client application herein, embodiments are not limited to emails. A communication service as disclosed herein may facilitate email exchange, messaging, online conferencing, audio communication, video communication, data sharing, application sharing, desktop sharing, and similar communication modes. Data associated with any of these modes may be stored in the mailboxes discussed herein.

A communication service according to embodiments may achieve “unlimited” storage for a single user by chaining mailboxes together. A normal user with, for example, less than 100 GB of data overall may either have just one primary mailbox 112 or have one primary mailbox 112 and one archive mailbox 114. The first archive mailbox 114 may be referred to as the archive “hierarchy” mailbox. However, when a user crosses over the predefined limit, they may end up having one primary mailbox 112, one archive “hierarchy” mailbox 114, and one or many archive “content” mailboxes 116.

Although the “archive” includes the hierarchy and content mailboxes, for a user it may appear as one single mailbox. For example, the user may see two nodes: one node for the primary mailbox 112 and one node for the “archive” (first archive mailbox 114 and additional “content” mailboxes 116). The user may have access to all the folders that the user created and the ones that the user imported along with system folders like Inbox and Sent Items.

When a communication application client requests content from a folder in any archive mailbox, the underlying service may provide that content if it is in the current archive mailbox as shown in the diagram. If the content is not in the mailbox, the service may provide a pointer to the mailbox and folder containing it. Allowing the client to directly request content from the appropriate mailbox, which could be on a different database/server than other archive mailboxes, may respect the tenets of brick architecture by avoiding server-side fan out calls.

When any one of the archive hierarchy/content mailbox reaches the mailbox quota, one or few of the folders in the mailbox may be moved to the other archive “content” mailboxes through an “auto-split” process, thereby freeing up space for growth. The auto-split threshold may be at the tenant level, in some implementations.

The complete folder hierarchy may be stored in the archive “hierarchy” and the archive “content” mailboxes. In some cases, the archive hierarchy mailbox may have the “writable” most recent copy of the folder hierarchy. The folder hierarchy in the archive content mailboxes may be updated periodically using a synchronization process. The end user, when accessing the “archive”, may connect only to the archive hierarchy mailbox. From there, all folder/content requests may be redirected appropriately.

In the example configuration of FIG. 1A, the additional mailboxes 116 are chained to the first archive mailbox 114 in a transparent manner to the user 108. Embodiments are not limited to this example configuration, however. FIGS. 1B and 1C below illustrate additional configurations.

In the example configuration of FIG. 1B, the mail application 110 is configured with a primary mailbox (cached) 112 and the additional archive mailboxes 116 are chained directly to the primary mailbox 112. The first one of the additional archive mailboxes 116 may be configured to contain the hierarchy information as described above.

The auto-split or data partitioning process may include chaining of partitions created on the fly based on mailbox size, items counts, and/or ingestion size. A size limit for the homogeneous partitions may be selected to ensure optimal performance. Automatic size balancing and search across multiple partitions may be enabled. Moreover, folder based and other metadata based views across multiple partitions may be provided. The system may intelligently and securely determine partition where requested data resides. Partitions may be directly targeted by ingestion systems. The system may take care of intelligently distributing data to ensure individual partition limits are respected. The partitioning may be transparent to compliance management processes. Electronic discovery may be enabled to obtain knowledge of all user partitions from the system to return results from all owned partitions securely. Hold, records management, and comparable policies may be aware of all partitions of the user and maintain service level agreements.

In the example configuration of FIG. 1C, the mail application 110 is configured with a primary mailbox (cached) 112 and an archive mailbox 114. In this case, both the primary mailbox 112 and the archive mailbox 114 are chained with respective additional archive mailboxes 116 and 118. Thus, additional mailboxes and partitioning may be performed in a number of different configurations in a transparent manner to the user.

FIG. 2 illustrates an example user experience for an administrator of a communication service implementing large data management through multiple mailboxes.

The administration user experience 204 of mail application/service 202 exemplifies a user interface that may be used to manage mailboxes in a communication application. Various attributes 206 associated with mailboxes and user accounts such as users, permissions, compliance, organizations, protection, mail flow, and folders may be selected and available properties for those attributes set/defined. A list of users 208 may be provided to enable an administrator to select among them and perform administrative tasks.

In an application/service according to embodiments, additional controls 210 may be provided to enable additional archive mailboxes, define archive type, or archive location. In some examples, a system according to embodiments may allow a generic way to request mailbox locations of any given type for a given directory object (e.g., obtain the location of a group's cloud mailbox). The system may also allow a generic way to manage mailbox locations regardless of mailbox type. For example, load balance all mailboxes that meet a particular criteria regardless of their nature and the attributes used to store that location on a directory entry.

FIG. 3 illustrates example operations on a communication system with multiple mailboxes.

As discussed previously, the additional (or extension) mailboxes may be implemented in a transparent manner to the user, where items such as folders may be stored in various mailboxes with pointers to those in other mailboxes being placed in the primary mailbox or the first archive mailbox. Thus, a user may click on a folder that exists in a different mailbox and open the folder and see its contents without a noticeable difference.

If all items of a conversation are within a single folder, browsing items in both conversation and item views may be possible. However, if a conversation has items spread over multiple folders (e.g., item 1 and item 2 are part of the conversation, mailbox 1 and mailbox 2 belong to the set of archive mailboxes, not the primary mailbox), conversation and item views may be adjusted accordingly.

In viewing items in archive, if the user selects “all mailboxes” when switching between item and conversation view, the view settings may apply to all folders, wherever they are located. When switching between item and conversation view, if the user selects “this folder”, the view settings may apply only to that folder (not its subfolders).

When a folder is moved, the communication application may be able to simply update the view and show the moved folder and its constituents under the target folder within an acceptable amount of time. Multiple folders selection may possible and move operations of multiple folders may be supported. If a user tries to move a small number of items/items of small size, cross server operations through the client may be fast and complete quickly. If a user tries to move a large number of items/items of large size, cross server operations through the client may not be fast. In such a scenario, a message to the user may be displayed letting them know that the operation has been queued and may complete within a particular time (depending on the size of items being moved, other operations on mailbox, store health, network health etc.). During the time that the operation is queued, if the user makes changes to the source list (like adding an item or deleting an item), the changes may be ignored, prevented, or considered. Once a move is queued, another move/copy on the same set of items/subset of items may fail with a message to the user indicating a different move is already queued and they have to wait until it completes.

Copy operations may be treated similar to move operations as described above. When a new folder is created, the view may be updated to reflect the new folder, which may inherit the permissions of the parent folder. Creation of the new folder may be performed through a hierarchy update operation.

Deleted items may be moved to a designated deleted items container, from which they may be recoverable. If items are recovered from the deleted items container, they may be moved back to their original location (folder).

Similar to folders and comparable items, additional mailboxes (extension mailboxes 308) themselves may also be subject to various operations. FIG. 3 illustrates some examples. Upon creation 304 of a mailbox (primary) 306 for user 302, extension mailboxes 308 may be created as the user approaches storage limits of existing mailbox(es). If inactivity is detected (310) after a predefined period of time, the one or more of the extension mailboxes (or even the primary mailbox 306) may be placed on hold (312) and removed permanently (316) upon expiration of the hold period. The mailboxes may also be removed permanently upon detection of a “remove” or hard delete command (314).

Upon detection of soft delete or hard delete command (310), one or more of the extension mailboxes (or even the primary mailbox 306) may be removed buy recoverable during a recovery period (312). During the recovery period, the mailboxes may be recovered 316 or removed permanently upon detection of a command (314).

The example scenarios and schemas in FIG. 1A through 3 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Providing large data management in a communication application through multiple mailboxes may be implemented in configurations employing fewer or additional components in applications and user interfaces. Furthermore, the example schema and components shown in FIG. 1A through 3 and their subcomponents may be implemented in a similar manner with other values using the principles described herein.

The technical advantages of providing large data management in a communication application through multiple mailboxes may include increased efficiency in network usage, reduced processor usage (reducing need to access exported data), improved user efficiency, and improved user interaction performance by allowing management of large amounts and variety of communication related data without extra steps to access the data.

FIG. 4 is an example networked environment, where embodiments may be implemented. A communication application or service configured to manage large amounts of data through the use of multiple mailboxes in a transparent manner to the user may be implemented via software executed over one or more servers 406 such as a hosted service. The platform may communicate with client applications on individual computing devices such as a smart phone 413, a mobile computer 412, or desktop computer 411 (‘client devices’) through network(s) 410.

Client applications executed on any of the client devices 411-413 may facilitate communications via application(s) executed by servers 406, or on individual server 404. The communication application or service may configure as many as needed archive mailboxes. The additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application or associated service. The communication application or service may store the item in data store(s) 408 directly or through database server 402.

Network(s) 410 may comprise any topology of servers, clients, Internet service providers, and communication media. A system according to embodiments may have a static or dynamic topology. Network(s) 410 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 410 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 410 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 410 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 410 may include wireless media such as acoustic, RF, infrared and other wireless media.

Many other configurations of computing devices, applications, data sources, and data distribution systems may be employed to provide management of large amounts of data in communication applications through the use of multiple mailboxes in a transparent manner to the user. Furthermore, the networked environments discussed in FIG. 4 are for illustration purposes only. Embodiments are not limited to the example applications, modules, or processes.

FIG. 5 is a block diagram of an example computing device, which may be used to implement large data management in a communication application through multiple mailboxes.

For example, computing device 500 may be used as a server, desktop computer, portable computer, smart phone, special purpose computer, or similar device. In an example basic configuration 502, the computing device 500 may include one or more processors 504 and a system memory 506. A memory bus 508 may be used for communicating between the processor 504 and the system memory 506. The basic configuration 502 is illustrated in FIG. 5 by those components within the inner dashed line.

Depending on the desired configuration, the processor 504 may be of any type, including but not limited to a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. The processor 504 may include one more levels of caching, such as a level cache memory 512, one or more processor cores 514, and registers 516. The example processor cores 514 may (each) include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof. An example memory controller 518 may also be used with the processor 504, or in some implementations the memory controller 518 may be an internal part of the processor 504.

Depending on the desired configuration, the system memory 506 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.) or any combination thereof. The system memory 506 may include an operating system 520, a communication service/application 522, and program data 524. The communication service/application 522 may include a mailbox management module 526 to increase data limit for a user by introducing additional archive mailboxes as the original archive fills up or subsequently added archive mailboxes fill up. The additional mailboxes may be integrated into the architecture of the communication application such that their use is transparent to the user and/or an administrator of the communication application/service 522. The program data 524 may include, among other data, mailbox data 528 that may be used to facilitate communications, as described herein.

The computing device 500 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 502 and any desired devices and interfaces. For example, a bus/interface controller 530 may be used to facilitate communications between the basic configuration 502 and one or more data storage devices 532 via a storage interface bus 534. The data storage devices 532 may be one or more removable storage devices 536, one or more non-removable storage devices 538, or a combination thereof. Examples of the removable storage and the non-removable storage devices include magnetic disk devices such as flexible disk drives and hard-disk drives (HDDs), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSDs), and tape drives to name a few. Example computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.

The system memory 506, the removable storage devices 536 and the non-removable storage devices 538 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the computing device 500. Any such computer storage media may be part of the computing device 500.

The computing device 500 may also include an interface bus 540 for facilitating communication from various interface devices (for example, one or more output devices 542, one or more peripheral interfaces 544, and one or more communication devices 546) to the basic configuration 502 via the bus/interface controller 530. Some of the example output devices 542 include a graphics processing unit 548 and an audio processing unit 550, which may be configured to communicate to various external devices such as a display or speakers via one or more A/V ports 552. One or more example peripheral interfaces 544 may include a serial interface controller 554 or a parallel interface controller 556, which may be configured to communicate with external devices such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 558. An example communication device 546 includes a network controller 560, which may be arranged to facilitate communications with one or more other computing devices 562 over a network communication link via one or more communication ports 564. The one or more other computing devices 562 may include servers, computing devices, and comparable devices.

The network communication link may be one example of a communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR) and other wireless media. The term computer readable media as used herein may include both storage media and communication media.

The computing device 500 may also be implemented as a part of a general purpose or specialized server, mainframe, or similar computer that includes any of the above functions. The computing device 500 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.

Example embodiments may also include methods to provide management of large amounts of data in communication applications through the use of multiple mailboxes in a transparent manner to the user. These methods can be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, of devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be collocated with each other, but each can be only with a machine that performs a portion of the program. In other embodiments, the human interaction can be automated such as by pre-selected criteria that may be machine automated.

FIG. 6 illustrates a logic flow diagram of a method to provide large data management in a communication application through multiple mailboxes, according to embodiments. Process 600 may be implemented on a computing device such as the computing device 600 or other system.

Process 600 begins with operation 610, where a communication application may detect that a predefined size threshold of a mailbox associated with a user is about to be reached. The mailbox may be a main mailbox (cached) or an archive mailbox. At operation 620, the communication application/service may create one or more additional mailboxes for the user. Depending on the type of the original mailbox (main or archive), the additional mailboxes may be associated with that mailbox.

At operation 630, communication application related data may be stored in the one or more additional mailboxes, where data in the mailbox and in the one or more additional mailboxes may be made available for one or more functionalities of the communication application in a transparent manner to the user.

The operations included in process 600 are for illustration purposes. Management of large amounts of data in communication applications through the use of multiple mailboxes in a transparent manner to the user may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.

According to some examples, a method executed on a computing device to provide large data management in a communication application through multiple mailboxes is described. An example method may include detecting a predefined size threshold of a mailbox associated with a user being reached; creating one or more additional archive mailboxes for the user; and storing communication application related data in the one or more additional archive mailboxes, where data in the mailbox and in the one or more additional archive mailboxes are available for one or more functionalities of the communication application in a transparent manner to the user.

According to other examples, the mailbox may be one of a primary mailbox and a first archive mailbox, and the method may also include creating the one or more additional archive mailboxes in chained manner connected to one of the primary mailbox and the first archive mailbox. The method may further include enabling the user to see a first node representing the primary mailbox and a second node representing the first archive mailbox and the one or more additional archive mailboxes. The method may also include storing the primary mailbox, the first archive mailbox, and the one or more additional archive mailboxes in one or more data stores, where the data stores include one of local data stores and online data stores.

According to further examples, the method may also include managing storage of the primary mailbox, the first archive mailbox, and the one or more additional archive mailboxes through one or more servers. The method may further include for communication application related data not stored in the primary mailbox or the first archive mailbox, creating one or more pointers to respective additional archive mailboxes in the primary mailbox or the first archive mailbox.

According to yet other examples, the method may also include upon detecting one of the primary mailbox, the first archive mailbox, and the one or more additional archive mailboxes reach a storage threshold, moving data to one or more other additional archive mailboxes through data partitioning. The data partitioning may include chaining of partitions created dynamically based on one or more of a mailbox size, an item count, and an ingestion size. The storage threshold may be defined at a tenant level within a communication service.

According to other examples, a computing device to provide large data management in a communication service through multiple mailboxes is described. The computing device may include a memory configured to store instruction associated with the communication service and one or more processors configured to execute one or more applications associated with the communication service in conjunction with the instructions stored in the memory. The one or more applications may include a communication application configured to facilitate exchange of communication in a plurality of modes between users and a data management application configured to manage communication application related data through mailboxes associated with the users and user groups. The data management application may be further configured to detect a predefined size threshold of an archive mailbox associated with a user being reached; create one or more additional archive mailboxes for the user; and store the communication application related data in the one or more additional archive mailboxes, where data in the archive mailbox and in the one or more additional archive mailboxes are available for one or more functionalities of the communication application in a transparent manner to the user.

According to further examples, the data management application may be further configured to store a folder hierarchy associated with the user in the archive mailbox and in one or more additional archive mailboxes designated as archive content mailboxes, and/or update the folder hierarchy stored in the archive content mailboxes through a periodic synchronization. The data management application may also be configured to partition data in one or more of the archive mailbox and the one or more additional archive mailboxes upon detecting the archive mailbox or the one or more additional archive mailboxes reach a storage threshold by chaining of partitions created dynamically based on one or more of a mailbox size, an item count, and an ingestion size.

According to yet other examples, the data management application may be further configured to enable automatic size balancing across the one or more additional archive mailboxes and searches across multiple partitions, and/or enable folder based and metadata based views across multiple partitions. The data management application may also be configured to provide partition information to one or more of an electronic discovery application, a records management application, and a compliance application. The plurality of modes may include one or more of an email exchange, a messaging exchange, an online conference, an audio communication, a video communication, a data sharing session, an application sharing session, and a desktop sharing session.

According to further examples, a computer-readable memory device with instructions stored thereon to provide large data management in a communication service through multiple mailboxes is described. The instructions may include detecting a predefined size threshold of an archive mailbox associated with a user being reached; creating one or more additional archive mailboxes for the user in a chained manner connected to the archive mailbox, where a folder hierarchy associated with the user is stored in the archive mailbox and in one or more additional archive mailboxes designated as archive content mailboxes; and storing communication application related data in the one or more additional archive mailboxes, where data in the archive mailbox and in the one or more additional archive mailboxes are available for one or more functionalities of the communication application in a transparent manner to the user.

According to some examples, the instructions may further include applying view settings to all folders independent of a folder location if the user selects “all mailboxes” when switching between an item view and a conversation view and applying the view settings to a selected folder if the user selects “this folder”. The communication application related data may include one or more of emails, calendar items, attachments, tasks, contact cards, online conference recordings, audio communication recordings, video communication recordings, and text messages.

The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments. 

What is claimed is:
 1. A method executed on a computing device to provide data management in a communication application, the method comprising: receiving data associated with the communication application; storing the data in a first mailbox associated with a user; detecting a predefined size threshold of the first mailbox being reached based on an amount of the data associated with the communication application stored in the first mailbox; in response to detecting the predefined size threshold of the first mailbox being reached, automatically creating a second mailbox in a chained manner with the first mailbox, storing at least a portion of the data associated with the communication application in the second mailbox, and providing data stored in the second mailbox in a transparent manner to the user within the communication application; and in response to detecting a particular period of inactivity within the second mailbox, removing the second mailbox.
 2. The method of claim 1, further comprising: enabling display of a node representing the first mailbox and the second mailbox.
 3. The method of claim 1, further comprising: storing the first mailbox and the second mailbox in an online data store.
 4. The method of claim 1 further comprising: managing storage of the first mailbox and the second mailbox through a server.
 5. The method of claim 1 further comprising: storing a pointer to the second mailbox in the first mailbox.
 6. The method of claim 1, wherein storing at least the portion of the data associated with the communication application in the second mailbox includes moving at least the portion of the data to the second mailbox through data partitioning.
 7. The method of claim 6, wherein the data partitioning includes dynamically creating a plurality of chained partitions of the data based on at least one selected from a group consisting of a mailbox size, an item count, and an ingestion size.
 8. The method of claim 1, wherein the predefined size threshold is defined at a tenant level.
 9. A computing device to provide large data management in a communication service through multiple mailboxes, the computing device comprising: a communication interface configured to facilitate exchange of a communication between a plurality of users associated with the communication service, wherein the communication includes at least one selected from a group consisting of an email exchange, a messaging exchange, an online conference, an audio communication, a video communication, a data sharing session, an application sharing session, and a desktop sharing session; a memory configured to store instructions associated with the communication service; and a processor configured, via execution of the instructions stored in the memory, to: receive data associated with the communication service; store the data in a first mailbox associated with a user; detect a predefined threshold of the first mailbox being reached based on an amount of the data associated with the communication service stored in the first mailbox; in response to detecting the predefined threshold of the first mailbox being reached, automatically create a second mailbox in a chained manner with the first mailbox, store at least a portion of the data in the second mailbox, and provide data stored in the second mailbox in a transparent manner to the user within the communication service; and in response to detecting a particular period of inactivity within the second mailbox, remove the second mailbox.
 10. The computing device of claim 9, wherein the processor is further configured to: designate the second mailbox as an archive content mailbox; and store a folder hierarchy associated with the user in the first mailbox and in the second mailbox.
 11. The computing device of claim 10, wherein the processor is further configured to: Periodically synchronize the folder hierarchy stored in the second mailbox with the folder hierarchy stored in the first mailbox.
 12. The computing device of claim 9, wherein the processor is configured to store at least the portion of the data in the second mailbox by dynamically creating a plurality of chained partitions of the data based on at least one selected from a group consisting of a mailbox size, an item count, and an ingestion size.
 13. The computing device of claim 12, wherein the processor is further configured to: enable automatic size balancing across the first mailbox and the second mailbox; and enable a search across multiple partitions included in the plurality of chained partitions.
 14. The computing device of claim 12, wherein the processor is further configured to: enable a folder-based view and a metadata-based view across multiple partitions included in the plurality of chained partitions.
 15. The computing device of claim 12, wherein the processor is further configured to: provide information regarding the plurality of chained partitions to at least one selected from a group consisting of an electronic discovery application, a records management application, and a compliance application.
 16. A computer-readable memory device with instructions stored thereon to provide, when executed by a processor, large data management in a communication service through multiple mailboxes, the instructions comprising: receiving data associated with the communication service; storing the data in a first mailbox associated with a user; detecting a predefined size threshold of the first mailbox being reached based on an amount of the data associated with the communication service stored in the first mailbox; in response to detecting the predefined size threshold of the first mailbox being reached, automatically creating a second mailbox in a chained manner with the first mailbox, storing at least a portion of the data associated with the communication service in the second mailbox, and providing data stored in the second mailbox in a transparent manner to the user within the communication service; and in response to detecting a particular period of inactivity within the second mailbox, removing the second mailbox.
 17. The computer-readable memory device of claim 16, wherein the instructions further comprise: in response to receiving a first user selection of “all mailboxes” when switching between an item view and a conversation view, applying a view setting to all folders independent of a folder location; and in response to a second user selection of “this folder” when switching between the item view and the conversation view, applying the view setting to a selected folder.
 18. The computer-readable memory device of claim 16, wherein the data associated with the communication service includes at least one selected from a group consisting of an email, a calendar item, an attachment, a task, a contact card, an online conference recording, an audio communication recording, a video communication recording, and a text message. 